Summary

• extract the getNamedBackups facade out of lib/storage.ts on top of the latest storage leaf
• keep named backup listing behavior unchanged while slimming the storage facade on the active chain
• add a focused test for the new named backups entry helper

Validation

• npm run typecheck
• npm run lint -- lib/storage/named-backups-entry.ts lib/storage.ts test/named-backups-entry.test.ts
• npm run test -- test/named-backups-entry.test.ts

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Greptile Summary

this pr extracts the getNamedBackups wiring out of lib/storage.ts into a new lib/storage/named-backups-entry.ts facade, following the same leaf-entry DI pattern used by restoreAccountsFromBackupEntry and siblings. behavior is unchanged; storage.ts slims down by delegating to the new helper.

• new file lib/storage/named-backups-entry.ts: thin facade accepting injected getStoragePath, collectNamedBackups, loadAccountsFromPath, and logDebug — all forwarded directly to collectNamedBackups, no logic added
• lib/storage.ts: getNamedBackups now delegates to getNamedBackupsEntry; the call-site wiring is identical to the pre-refactor inline call
• test/named-backups-entry.test.ts: single focused vitest case asserting the wiring — happy path only; non-empty result passthrough is unexercised
• circular type import: named-backups-entry.ts imports NamedBackupSummary from ../storage.js rather than from ./named-backups.js where it is actually defined, creating a type-level cycle in the module graph; harmless at runtime but worth fixing
• lib/AGENTS.md / lib/storage directory listing not updated to include the new file — minor maintenance gap

Confidence Score: 5/5

• safe to merge — pure refactor, behavior unchanged, only non-blocking P2 style issues remain
• the change is a straightforward delegation extraction with no logic delta. the only issues are a type-only circular import (erased at compile time, no runtime effect) and a single test case where a second passthrough assertion would be cleaner. both are P2 follow-ups, not blockers.
• lib/storage/named-backups-entry.ts — fix the NamedBackupSummary import source

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant caller as caller
    participant storage as lib/storage.ts<br/>getNamedBackups()
    participant entry as lib/storage/named-backups-entry.ts<br/>getNamedBackupsEntry()
    participant collector as lib/storage/named-backups.ts<br/>collectNamedBackups()

    caller->>storage: getNamedBackups()
    storage->>entry: getNamedBackupsEntry({ getStoragePath, collectNamedBackups, loadAccountsFromPath, logDebug })
    entry->>entry: params.getStoragePath()
    entry->>collector: collectNamedBackups(storagePath, { loadAccountsFromPath, logDebug })
    collector-->>entry: NamedBackupSummary[]
    entry-->>storage: NamedBackupSummary[]
    storage-->>caller: NamedBackupSummary[]

This is a comment left during a code review.
Path: lib/storage/named-backups-entry.ts
Line: 1

Comment:
**circular type import — prefer direct source**

`NamedBackupSummary` is defined in `./named-backups.ts`, but this file imports it from `../storage.js`. that creates a logical type-level cycle: `storage.ts` → `named-backups-entry.ts` → `storage.ts`. `import type` is erased at compile time so there's no runtime issue, but the cycle still pollutes the module graph and can confuse tools like `madge`. import directly from the definition site to break the cycle:

```suggestion
import type { NamedBackupSummary } from "./named-backups.js";
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: test/named-backups-entry.test.ts
Line: 6-22

Comment:
**missing non-empty passthrough coverage**

the single test only exercises the `[]` return path. given the 80% vitest coverage threshold enforced on this codebase, consider adding a second case where `collectNamedBackups` resolves to a non-empty `NamedBackupSummary[]` and asserting the result is forwarded unchanged — verifies the return value isn't accidentally dropped or mutated. error-propagation from `collectNamedBackups` throwing is also unexercised, though for this thin a wrapper that's optional.

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: "refactor: extract la..."}